Fix blocking calls for gRPC even though using Reactor#435
Conversation
artursouza
left a comment
There was a problem hiding this comment.
Thanks for the PR, it is promising. There are two points of contention for me here. First, the unit tests for hot mono should stay - that is a big deal when dealing with Reactor and we found it the hard way early in this project. Second, we should not wrap (or catch) throwables otherwise we end up in situations where we handle or wrap OutOfMemoryError, for example.
|
The only thing now is to bring back the hot mono unit tests. |
Codecov Report
@@ Coverage Diff @@
## master #435 +/- ##
============================================
- Coverage 83.44% 83.30% -0.14%
- Complexity 851 859 +8
============================================
Files 74 74
Lines 2519 2540 +21
Branches 256 256
============================================
+ Hits 2102 2116 +14
- Misses 296 302 +6
- Partials 121 122 +1
Continue to review full report at Codecov.
|
Description
Make DaprClientGrpc truly async and update unit tests.
Issue reference
We strive to have all PR being opened based on an issue, where the problem or feature have been discussed prior to implementation.
Reference: #434
Checklist
Please make sure you've completed the relevant tasks for this PR, out of the following list: